翻訳と辞書
Words near each other
・ Origins (cosmetics)
・ Origins (Eluveitie album)
・ Origins (God Is an Astronaut album)
・ Origins (Judge Dredd story)
・ Origins (Steve Roach album)
・ Origins and architecture of the Taj Mahal
・ Origins Award
・ Origins Canada
・ Origins Game Fair
・ Origins Institute
・ Origins of Asian martial arts
・ Origins of Australian rules football
・ Origins of baseball
・ Origins of Christianity
・ Origins of Czechoslovakia
Origins of enterprise architecture
・ Origins of Falkland Islanders
・ Origins of global surveillance
・ Origins of Hutu and Tutsi
・ Origins of Judaism
・ Origins of Lahore
・ Origins of Life and Evolution of Biospheres
・ Origins of names of cities and towns in Hong Kong
・ Origins of New Mexico Families
・ Origins of North Indian and Pakistani foods
・ Origins of opera
・ Origins of Paleoindians
・ Origins of Rabbinic Judaism
・ Origins of rock and roll
・ Origins of society


Dictionary Lists
翻訳と辞書 辞書検索 [ 開発暫定版 ]
スポンサード リンク

Origins of enterprise architecture : ウィキペディア英語版
Origins of enterprise architecture

The first publication to use the exact term enterprise architecture was a National Institute of Standards Special Publication on the challenges of information system integration. The overview states "This panel addressed the role of architectures and standards in support of management throughout an enterprise."
This original use is often incorrectly attributed to John Zachman's 1987 paper, which did not use the term "Enterprise Architecture". The scope of the report by the NIST "enterprise architecture" panel may be directly compared to Zachman's current thinking presented in the 1987 article which is as follows: "With Increasing size and complexity of the Implementations of Information systems it Is necessary to use some logical construct (or architecture) for defining and controlling the interfaces and the Integration of all of the components of the system. ... The discussion Is limited to architecture and does not Include a strategic planning methodology."
In the 1989 NIST article, an enterprise architecture is described as consisting of several levels. The top level is "Business Unit Architecture". The document describes this as follows: "A Business Unit may portray either a total corporate entity or a corporate sub-unit. Architecture at this level establishes a framework for satisfying both internal information needs and the information and data needs imposed by external organizations. These external organizations include cooperating organizations, customers, and federal agencies. The information and data needs at this level impose requirements to be satisfied at lower levels of the architecture, with increasing attention to technical considerations."
The 1989 NIST document continues " The representation of the Business Unit architecture shows organizational units and their relationships, as well as specific standards, policies, and procedures that enable or constrain the accomplishment of the overall enterprise mission."
By examination the evidence shows that Zachman's concept was the creation of an individual information system, perhaps composed of subsystems, optimized for a business case. However the NIST conception describes the management of all the information system in a business unit which may be the whole enterprise.
Zachman did not use the exact term "enterprise architecture" in a publication until several years later.
== References ==



抄文引用元・出典: フリー百科事典『 ウィキペディア(Wikipedia)
ウィキペディアで「Origins of enterprise architecture」の詳細全文を読む



スポンサード リンク
翻訳と辞書 : 翻訳のためのインターネットリソース

Copyright(C) kotoba.ne.jp 1997-2016. All Rights Reserved.